Individualized audit log access control for virtual machines

ABSTRACT

To provide enhanced operation of computing systems to control access to audit logging resources by virtual machines, various systems, apparatuses, methods, and software are provided herein. In a first example, a method of operating a computing system is provided. The method includes receiving requests for audit credentials from virtual machines, and responsively providing individualized audit credentials to the virtual machines based at least on identities of the virtual machines. The method also includes, in the audit system, authorizing storage of audit data transferred by the virtual machines based at least on the individualized audit credentials accompanying the audit data. The method also includes, in the authorization system, selectively de-authorizing one or more of the virtual machines and reporting information regarding the de-authorized one or more of the virtual machines to the one or more audit systems.

RELATED APPLICATIONS

This application hereby claims the benefit of and priority to U.S.Provisional Patent Application 62/003,802, titled “SYSTEMS, METHODS, ANDSOFTWARE TO PROVIDE ACCESS CONTROL IN CLOUD COMPUTING ENVIRONMENTS,”filed May 28, 2014, and which is hereby incorporated by reference in itsentirety. This application also hereby claims the benefit of andpriority to U.S. Provisional Patent Application 62/035,251, titled“INDIVIDUALIZED AUDIT LOG ACCESS CONTROL FOR VIRTUAL MACHINES,” filedAug. 8, 2014, and which is hereby incorporated by reference in itsentirety.

TECHNICAL FIELD

Aspects of the disclosure are related to the field of access control incloud computing environments, and in particular, providing accesscontrol for virtual machines in cloud computing environments.

TECHNICAL BACKGROUND

Virtualized computer systems are becoming increasingly deployed incomputing environments. These virtualized computer systems includevirtual servers and other virtual machines that host a variety ofsoftware applications. Virtual servers can be scaled up or downon-the-fly based on demand, among other factors, to allow forinfrastructure flexibility, faster deployment of applications and data,cost control, and adaptability. Cloud computing systems can use thesevirtualized computer systems to provide flexible computing resources toend users. Cloud computing systems allow for users spread over a varietyof geographic locations to access resources of these virtualizedcomputer systems, such as databases, applications, web content, or otherdigital data, services, or content.

Cloud Service Providers (CSPs) such as Amazon, Google, Rackspace, andOpenStack deploy physical hardware such as servers, networkinfrastructure, and connectivity for the cloud computing systems to hostdigital products and services from various remote locations. Cloudservice customers can employ the resources provided by the various CSPswithout having to purchase and maintain physical equipment.

Access to cloud resources of the various CSPs is managed throughpermissions. These permissions could include usernames and passwords, aswell as other credentialing information. However, in cloud computingenvironments, access control beyond initial user authorization islimited. The current access control systems lack the ability to manageaccess to resources accessed by virtual machines.

OVERVIEW

To provide enhanced operation of computing systems to control access toaudit logging resources by virtual machines, various systems,apparatuses, methods, and software are provided herein. In a firstexample, a method of operating a computing system is provided. Themethod includes receiving requests for audit credentials from virtualmachines, and responsively providing individualized audit credentials tothe virtual machines based at least on identities of the virtualmachines. The method also includes, in the audit system, authorizingstorage of audit data transferred by the virtual machines based at leaston the individualized audit credentials accompanying the audit data. Themethod also includes, in the authorization system, selectivelyde-authorizing one or more of the virtual machines and reportinginformation regarding the de-authorized one or more of the virtualmachines to the one or more audit systems.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the disclosure can be better understood with referenceto the following drawings. The components in the drawings are notnecessarily to scale, emphasis instead being placed upon clearlyillustrating the principles of the present disclosure. Moreover, in thedrawings, like reference numerals designate corresponding partsthroughout the several views. While several embodiments are described inconnection with these drawings, the disclosure is not limited to theembodiments disclosed herein. On the contrary, the intent is to coverall alternatives, modifications, and equivalents.

FIG. 1 is a system diagram illustrating a computing environment.

FIG. 2 is a sequence diagram illustrating a method of operation of acomputing environment.

FIG. 3 is a system diagram illustrating a computing environment.

FIG. 4 is a sequence diagram illustrating a method of operation of acomputing environment.

FIG. 5 is a block diagram illustrating an example computing system.

DETAILED DESCRIPTION

The various figures and descriptions included herein discuss manyexamples for enhanced access control for virtual machines in a computingenvironment. The access control can include restricting access byvirtual machines to various data resources, such as databases, othervirtual machines, application storage, user data, among other dataresources. The access control can allow for individualizedauthentication or authorization of virtual machines to various dataresources, even when the virtual machines are instantiated or replicatedfrom the same virtual images. Although these virtual machines can behosted in a cloud computing environment, the examples herein are notlimited to cloud systems.

As a first example of a computing system, FIG. 1 is provided. FIG. 1 isa system diagram illustrating computing system 100. Computing system 100includes end user system 101, user interface system 110, storage system120, execution system 130, authorization system 140, and data resource150. The various elements of FIG. 1 are each configured to communicateover one or more data networks, such as over various packet links.Although physical network links are not shown in FIG. 1 for clarity, itshould be understood that one or more network links can be includedbetween each element of FIG. 1. For example, end user system 101 anduser interface system 110 can communicate over one or more packetnetworks, which can include the Internet. Various physical computinginfrastructure can host user interface system 110, storage system 120,execution system 130, such as a distributed computing system. Likewise,computer systems, such as computer servers and the like, can compriseauthorization system 140 as well as data resource 150.

In operation, end user system 101 can interact with user interfacesystem 110 to establish, instantiate, configure, and alter variousvirtual machines and associated properties. User interface system 110can include a front-end interface provided over a web interface andaccessed in a browser application on end user system 101. In otherexamples, an application programming interface (API) system is employedfor end user system 101 to interface with user interface system 110 tocontrol the operations of virtual machines.

Storage system 120 includes one or more virtual machine images, such asvirtual machine image 121. These virtual machine images includeoperating systems, user and system applications, various modules,network service applications, among other computing resources that canbe instantiated and subsequently operate similar to a physical computingsystem. When activity of an end user or other management service causesa virtual machine to be active, the virtual machine is instantiated byexecution system 130. Any number of virtual machines can be concurrentlyactive in execution system 130, which can include any number of virtualmachine handling software elements, such as hypervisors, resourcemanagers, virtual network elements, among other software elements. Thesevarious active virtual machines can be instantiated from a shared orsame virtual image, with many replicated copies of the same virtualmachine image being executed concurrently by execution system 130.

In FIG. 1, virtual machine image 121 is instantiated as virtual machine131. Instantiated virtual machine 131 can then execute variousapplications, manage computing resources, distribute data to end users,among other activities that a computing system typically performs.However, in FIG. 1, virtual machine image 121 also includes securitymodule 122. Security module 122 is included in the data which forms theimage of virtual machine image 121, and can comprise a startup script,executable module, user application, among other modules. Once virtualmachine image 121 has been instantiated as virtual machine 131, securitymodule 132 is executed by virtual machine 131. This execution can beautomatic upon boot-up of various operating system components of virtualmachine 131, or can be responsive to virtual machine 131 seeking out anexternal data resource, such as resource 150, among other executiontriggers. Token 160 is used by virtual machine 131 to establishcredentials for virtual machine 131 to access external resources, suchas resource 150.

FIG. 2 is provided to further illustrate the operations of FIG. 1. FIG.2 is a sequence diagram illustrating a method of operation of FIG. 1. InFIG. 2, end user system 101 provides token 160 for instantiated virtualmachine 131. Token 160 can be provided through user interface system 110by end user system 101, such as through a web interface, controlconsole, API, or other interface system. Token 160 can be provided withinstantiation commands issued by end user system 101, such as commandsto instantiate virtual machine image 121. In other examples, token 160can be provided after instantiation of virtual machine 131. In furtherexamples, end user system 101 requests token 160 from authorizationsystem 140 prior to instantiating virtual machine 131, and the accesstoken is provided by authorization system 140 to end user system 101.Operation ‘1’ of FIG. 1 illustrates an example initial tokendistribution by end user system 101, and operation ‘2’ of FIG. 2illustrates instantiation of virtual machine image 121 into virtualmachine 131.

Token 160 can comprise a datagram unique to virtual machine 131, such anencrypted code, security key, identifier, identity of end user system101, or other data, including combinations and variations thereof. Insome examples, token 160 comprises pseudo-random data, such as anencrypted key, used to uniquely identify a particular instance ofvirtual machine image 121. Token 160 can be generated or identified byend user system 101, or can be provided to end user system 101 byauthorization system 140. Token 160 can comprise an identity of end usersystem 101 or a user of end user system 101. The identity can allow forauditing of which users or end user systems desire to access particularresources, such as in healthcare auditing to establish traceabilitybetween data access and users. In other examples, token 160 comprises aunique code or encrypted key, and can be used for access control oraccess restriction to prevent unauthorized users from gaining access todata resources. Other configurations of token 160 are possible,including combinations thereof. Token 160 typically comprises one ormore packets which can include network addressing information thatidentifies virtual machine 131 or security module 132.

Token 160 can be provided to virtual machine 131 during instantiation,such as through user data or user parameters that are provided as aninput to virtual machine image 121 during an instantiation process.Security module 132 is configured to receive token 160 responsive toexecution of security module 132. For example, security module 132 cancomprise a startup script which uses token 160 as input data or userparameters provided during instantiation of virtual machine 131.Security module 132 transfers token 160 for delivery to authorizationsystem 140.

Responsive to receiving token 160, authorization system 140 transferscredentials 161, as shown by operations ‘3’ and ‘4’ in FIG. 1.Authorization system 140 provides credentials 161 for delivery tosecurity module 132 or virtual machine 131. These credentials are usedby virtual machine 131 to access a data resource, such as resource 150.Credentials 161 can comprise user credentials, such as a username,password, access code, PIN number, among other credentials, includingcombinations thereof. Credentials 161 can be specific to token 160,specific to virtual machine 131, or specific to a user of end usersystem 101. The issued credentials may be temporary or one-time use.

During execution of virtual machine 131, access to a data resource mightbe desired. This data resource, such as resource 150, can be external tovirtual machine 131 and require credentials in order to access theassociated data resources. For example, resource 150 can comprise adatabase system and virtual machine 131 desires to access data stored orhandled by that database system. Any data resource can be employed, suchas user applications, databases, digital media content resources,healthcare data, government data, or other data resources, includingcombinations thereof.

To access resource 150, virtual machine 131 provides credentials 161 toresource 150, as shown by operation ‘5’ in FIG. 1. Resource 150 mightoptionally check or verify credentials 161 before providing anyassociated data to virtual machine 131, such as in operation ‘6’ inFIG. 1. For example, resource 150 can verity credentials 161 withauthorization system 140. If the credentials are verified, then dataassociated with resource 150 can be transferred for delivery to virtualmachine 131. Credentials 161 are not necessarily verified withauthorization system 140 in all examples, such as when resource 150 canverify credentials 161 locally or when resource 150 initially providedcredentials 161 to authorization system 140. In yet further examples,responsive to receiving token 160, authorization system 140 can identifythe credentials and transfer the credentials for delivery to dataresource 150 and for delivery to the virtual machine 131.

If credentials 161 are not valid or fail associated verifications, thenresource 150 can deny access to virtual machine 131 for further accessto resource 150. However, if virtual machine 131 is verified usingcredentials 161, then further access to resource 150 is provided.Resource 150 and virtual machine 131 can establish a communicationsession which is authenticated by credentials 161, and virtual machine131 can continue to have access to resource 150 during the communicationsession.

As discussed above for FIGS. 1 and 2, individualized access credentialscan be provided to a virtual machine. The virtual machine can be basedupon a virtual machine image which can be used to establish manyinstances of the same virtual machine image. Thus, a shared virtualmachine image can be used to spawn or replicate many identical virtualmachines. Additionally, a particular instance of a first virtual machinemight replicate itself during execution of the first virtual machine.However, it can be difficult to allow individualized access control foreach identical or replicated virtual machine without changing theoriginal image data for each instance of a virtual machine. In theexamples herein, a token or other data is provided as user data or userparameters which are employed by a security module during instantiationof a virtual machine. This token can be unique to a virtual machine orunique to a user employing a virtual machine, and thus providesindividualized access control for a virtual machine that is instantiatedfrom the same virtual machine image as many other virtual machines. Asecurity module included in a virtual machine image, such as a startupscript, can receive a token provided by a user or other executing entitywhich can be used to establish credentials that are unique to thatparticular instance of a virtual machine. Authorization system 140provides credentials responsive to receiving a token from a virtualmachine, and that virtual machine can then receive individualizedcredentials for access control to various data resources. In thismanner, the same virtual machine image can be employed across manyreplications and instances which still allowing for individualizedidentification, access control, and auditing of each virtual machineindependently of each other without having to pre-customize each virtualmachine image to be different from each other.

In further examples, when a virtual machine is instantiated from ashared virtual machine image 121, a second virtual machine can beinstantiated from shared virtual machine image 121. This second virtualmachine can be instantiated responsive to end user commands or end useractivity, such as in end user system 101 or a second end user systemdifferent than end user system 101. The second end user system canprovide a second access token during instantiation of the second virtualmachine which can be employed by a security module of the second virtualmachine. The second access token is different than first access token160. Responsive to the second instantiation command, the second virtualmachine identified by the second instantiation command uses the secondaccess token as second user data for the second virtual machine duringinstantiation. In the second virtual machine, a security module isexecuted responsive to instantiation that transfers the second accesstoken for delivery to authorization system 140. In the second virtualmachine, second credentials are received responsive to the second accesstoken, and data resource 150 is accessed using the second credentials.The second credentials are different than first credentials 161. In yetfurther examples, instead of the second virtual machine beinginstantiated due to an instantiation command, the first virtual machine131 might decide to replicate due to loading or other conditions, usingthe same shared virtual machine image 121. The second access token canbe provided by an end user system during replication.

Returning to the elements of FIG. 1, end user system 101 comprises oneor more computing devices, such as a computer, tablet computer,smartphone, gaming console, kiosk computer, or other computing device,including combinations thereof. End user system 101 can be operated by auser, such as when a user interacts with an application provided by enduser system 101. For example, user interface system 110 could provideaccess to an e-commerce web site hosted on virtual machine 131, and enduser system 101 can include a customer accessing the web site in abrowser application to make purchases. In another example, userinterface system 110 can provide a healthcare application hosted onvirtual machine 131, and end user system 101 can comprise a customersigning up for healthcare insurance of the healthcare provider. In yetanother example, user interface system 110 can provide a financialapplication, such as a banking web site, online stock trading website,or 401(k) and Retirement Administration services web site hosted onvirtual machine 131. End user system is operated by a customer of thebank, online stock trading service, or 401(k) company.

User interface system 110 comprises user interface elements andcomputing systems configured to provide virtual machine control andinterfacing to end users. In some examples, end users are not aware ofusing virtual machines and user interface system 110 presents userinterfaces to end users which employ virtual machines responsive to enduser activity. In other examples, user interface system 110 providesadministration consoles or management interfaces for end users tocontrol and alter the operations of virtual machines, create andmaintain virtual machine images, manage security modules of virtualmachine images, among other operations. In yet further examples, userinterface system 110 comprises one or more servers for presenting webpages or user applications to end users. Responsive to end useractivity, such as web browsing activities or application selections, oneor more virtual machines can be instantiated to scale up load handlingcapabilities of the associated web pages or user applications. Userinterface system 110 is configured to receive tokens from end users andpass these tokens to virtual machines during instantiation.

User interface system 110 can be provided along with storage system 120and execution system 130 in a cloud computing environment, such asprovided by Cloud Service Providers (CSPs) such as Amazon, Google,Rackspace, and OpenStack, among others. The cloud computing environmentcan include a distributed computing environment with one or morephysical servers distributed over one or more geographic areas. Aplurality of virtual machines can be instantiated from a single sharedvirtual machine image responsive to user demand, load conditions,throughput needs, among other factors. For example, system load oraccess requests may increase due to end user demand. For instance,virtual machine 131 may be hosting an e-commerce or healthcare web site.At certain times there may be bursts of spikes in end-user requests. Forexample, in an e-commerce web site, there may be increased activity whena new product is launched or during sales, like Black Friday or CyberMonday. On a healthcare web site there may be spikes or bursts ofend-user activity when there is a deadline to sign up for coverage ornew plans are instituted. In order to accommodate the increased numberof requests, virtual machine 131 may be programmed to replicate or spawnto increase bandwidth to the application service. In other examples, anadministrator or other personnel may send a request to replicate orspawn virtual machine 131. Different tokens can be provide to eachinstance or replication of a virtual machine to allow that virtualmachine to retrieve credentials from authorization system 140.

Cloud computing environments that provide user interface system 110,storage system 120, and execution system 130, are representative of anyphysical or virtual computing system, device, or collection thereofcapable of hosting all or a portion of services provided to end users.Examples of cloud computing environment include, but are not limited to,server computers, web servers, application servers, rack servers, bladeservers, virtual machine servers, or tower servers, as well as any othertype of computing system, of which computing system 501 illustrated inFIG. 5 is representative.

Storage system 120 includes one or more non-transitory computer-readablestorage media, such as disk drives, disk arrays, solid state storagedrives, optical drives, magnetic storage systems, among other storagemedia. Storage system 120 stores one or more virtual machine imageswhich can be instantiated by execution system 130. Storage system 120can also store user data, application data, resource data, among otherdata, including combinations thereof.

Execution system 130 includes one or more processing systems thatexecute software instructions responsive to user activity and commandsissued by user interface system, among other systems. These processingsystems can be localized or distributed, and include or more processors,microprocessors, processing circuitry, cloud-based systems, or someother processing devices or software systems, and can be distributedamong multiple processing devices. Examples of execution system 130 canalso include software such as an operating system, logs, datastructures, databases, utilities, drivers, networking software, andother software stored on a non-transitory computer-readable medium.Execution system 130 also includes one or more network interfaces forexchanging network communications over one or more communication links.

Although not shown in FIG. 1 for clarity, computing system 100 caninclude network routing elements and network traffic handling elements.These network routing and handling elements can include wired orwireless network elements, such as packet networks and packet links thatcan each use metal, glass, optical, air, space, or some other materialas the transport media. The network routing and handling elements caneach use various communication protocols, such as Internet Protocol(IP), Ethernet, Time Division Multiplex (TDM), asynchronous transfermode (ATM), synchronous optical networking (SONET), hybrid fiber-coax(HFC), Universal Serial Bus (USB), circuit-switched, communicationsignaling, wireless communications, or some other communication format,including combinations, improvements, or variations thereof. Thesenetwork routing and handling elements can include direct links or caninclude intermediate networks, systems, or devices, and can includelogical network links transported over multiple physical links. Thesenetwork routing and handling elements can each include many differentsignals sharing the same associated link comprising resource blocks,access channels, paging channels, notification channels, forward links,reverse links, user communications, communication sessions, overheadcommunications, carrier frequencies, other channels, timeslots,spreading codes, transportation ports, logical transportation links,network sockets, packets, or communication directions.

Virtual machine 131, along with any other instantiated or replicatedvirtual machines, can provide an application service to end users. Thisapplication service can be representative of any application, softwareapplication, module, component, or collection thereof hosted incomputing system 100. Examples of an application service include, butare not limited to, healthcare applications, financial application,banking applications, credit card payment applications, electronicpayment applications, email applications, gaming applications, real-timecommunication applications, blogging and micro-blogging applications,social networking applications, and e-commerce applications, as well asany other type of application. Application services may be locallyinstalled and executed applications, streamed applications, mobileapplications, or any combination or variation thereof. In someimplementations, the application services may be a browser-basedapplication that executes in the context of a browser application.

Authorization system 140 comprises computer processing systems andequipment. Authorization system 140 can include communication or networkinterfaces, as well as computer systems, microprocessors, circuitry,cloud-based systems, or some other processing devices or softwaresystems, and can be distributed among multiple processing devices.Examples of authorization system 140 can also include software such asan operating system, logs, databases, utilities, drivers, networkingsoftware, and other software stored on a computer-readable medium.

Resource 150 includes computers, physical servers, virtual machines,virtual servers, applications, shared data resources, and shareddatabases. Resource 150 can be representative of any physical or virtualcomputing systems, devices, or collections thereof capable of providingdigital data resources to a virtual machine.

FIG. 3 is presented to illustrate a computing environment whereindividualized access to audit logging resources is established forvirtual machines. FIG. 3 is a system diagram illustrating computingsystem 300. Computing system 300 includes execution system 330,execution system 340, authorization system 350, audit log system 360,and audit system 320. The various elements of FIG. 3 are each configuredto communicate over one or more data networks, such as over variouspacket links. Although physical network links are not shown in FIG. 3for clarity, it should be understood that one or more network links canbe included between each element of FIG. 3. For example, executionsystem 330 and audit log system 360 can communicate over one or morepacket networks, which can include the Internet. Various physicalcomputing infrastructure can host execution system 330 and executionsystem 340, such as a distributed or cloud computing system. Likewise,computer systems, such as computer servers and the like, can compriseauthorization system 340, audit log system 360, and audit system 320.

In operation, one or more virtual machines are executed by an associatedexecution system. These virtual machines can deploy application servers,databases, media servers, or any other data handling, processing, ordistribution system. In some examples, each of execution systems 330 and340 are provided by different cloud computing platforms, such asdifferent CSPs. For example, virtual machines 331 and 333 are executedon execution system 330, while virtual machines 341 and 343 are executedon execution system 340, although other configurations are possible.

During normal operation of each virtual machine in FIG. 3, logging ofthe various functions and operations of each virtual machine can betracked. This logging can include audit logging to maintain a record foraudit purposes, such as for later review by audit system 320, amongother systems. The logging can include information related to useraccess, network sessions, timestamps of activities, virtual machinestartup/instantiation, replication times of virtual machines, loadconditions, network activity, processor event logging, operating systemevent logging, among any other logging functions. In the example shownin FIG. 3, this logging is provided by audit log system 360. Eachvirtual machine is configured to transfer log information for deliveryand storage by audit log system 360. However, when each virtual machineis replicated or instantiated from a shared or the same virtual machineimage, then differentiating which log entries should be associated witheach virtual machine can be difficult. Although a shared login orcredential can be used by all virtual machines instantiated from ashared virtual machine image, this shared login can lead to problemswith tracking individual virtual machines as well as controlling accessto an audit log on an individualized basis.

FIG. 4 is presented to illustrate individualized credentialing foraccessing audit log resources associated with virtual machines. FIG. 4is a sequence diagram illustrating a method of operation of elements ofsystem 300. In FIG. 4, virtual machine 331, after instantiation, isconfigured to request credentials for logging purposes. In FIG. 3, eachvirtual machine includes an associated security module, such as securitymodule 332 of virtual machine 331. This security module can include ascript or executable code which is configured to request auditcredentials from authorization system 350.

In FIGS. 3 and 4, virtual machine 331 provides at least an identity ofvirtual machine 331 for delivery to authorization system, as noted byoperation ‘1’ in FIG. 3. This identity can include a unique identifiergenerate by security module 332 to identify virtual machine 331 duringthe time that virtual machine 331 is active or instantiated. The uniqueidentifier can be a pseudo-random number. In other examples, theidentity can instead be a network address, such as an IP address or MACaddress of virtual machine 331. In other examples, further identityinformation is provided to authorization system 350, such as a token asdescribed in FIG. 1. This token can be provided by a user or end usersystem as user data or user parameters for use in receiving auditcredentials during an instantiation process of virtual machine 331 or astartup scripting process of security module 332.

Responsive to the identity information, authorization system 350 canverify the virtual machine and authorize the virtual machine to receiveaudit credentials for use in storing audit log information in audit logsystem 360. These credentials, namely credentials 371, are thentransferred for delivery to the virtual machine that requested them,such as virtual machine 331. In some cases, authorization system 350might deny authorization to a virtual machine for audit credentials,such as due to an invalid identity. Operation ‘2’ in FIG. 3 indicatesthe transfer of credentials 371. Credentials 371 can comprise usercredentials, such as a username, password, access code, PIN number,among other credentials, including combinations thereof. Credentials 371are specific to an identity provided or specific to virtual machine 331.The issued credentials may be temporary or one-time use.

Once credentials 371 are received by virtual machine 331, thesecredentials can accompany audit data 380 for logging by audit log system360. Audit log system 360 can selectively allow or deny storage of auditdata based on credentials provided by virtual machines. Instead of ausing a shared or the same credentials for all virtual machinesinstantiated from the same virtual machine image, audit log system 360uses individualized credentialing for each instance of a virtualmachine. For example, virtual machines 331 and 333 can be duplicatevirtual machines or instantiated from the same source virtual machineimage. However, each virtual machine 331 and 333 requests separatecredentials from authorization system 350, and authorization system 350provides individualized credentials for each virtual machine based inpart on the identity provided by the associated virtual machine. Auditdata 380 is shown being transferred in operation ‘3’ of FIG. 3, and canbe accompanied by the associated credentials. It should be understoodthat the credentials can precede or follow any associated audit data,and in some examples, a communication session can be established betweena virtual machine and audit log system 360 using the credentials. Oncethe communication session is established, then any audit data might beauthorized for storage based on a handshaking process using thecredentials.

In some examples, the credentials are verified internally to audit logsystem 360, such as when the credentials are also transferred byauthorization system 350 for delivery to audit log system 360 whentransferred to the associated virtual machine. In other examples, auditlog system 360 generates the credentials and provides the credentials toauthorization system 350, and thus the credentials can also be checkedor verified locally to audit log system 360. However, as shown in FIGS.3 and 4, audit log system 360 instead verifies the credentialsassociated with audit data 380 using authorization system 350. Inoperation ‘4’ of FIG. 3, audit log system 360 transfers a verificationmessage or authentication check 375 for delivery to authorization system350. Authorization system 350 can verify or deny the credentialsaccordingly, and respond with an authorization status message 376 thatindicates at least if the credentials are verified or denied. Audit logsystem 360 can store audit data 380 if the credentials are verified.

In another example, as shown in FIG. 4, virtual machine 343 requestscredentials using at least an identity. However, in this example,authorization system 350 denies authorization for virtual machine 343.This denial can arise from an incorrect or invalid identity, a propertyof audit log system 360, such as a time of day, day of the week, orsuch, that virtual machine 343 is allowed access to store audit data, orcan arise from detection of malicious or malfunctioning behavior ofvirtual machine 343. In further examples, virtual machine 343 might notinclude a security module and not request credentials from authorizationsystem 350. If virtual machine 343 nonetheless attempts to store auditdata 381 in audit log system 360, then audit log system 360 can denystorage of audit data 381 based on a lack of credentials or due tocredentials provided with audit data 381 being invalid or denied. Auditlog system 360 can verify any credentials associated with audit data381, and responsive to unverified or denied credentials can withoutstoring audit data 381. In further examples, responsive to failedverification using improper or invalid credentials, audit data log 360can report the failed credentials to authorization system 350 or toaudit system 320. This report can include information related tounauthorized access to store data in audit log system 360.

In further examples, once credentials have been granted for a particularvirtual machine, such as for virtual machine 331, these credentials canbe revoked at a later time. When audit log system 360 checks or verifiesassociated credentials with authorization system 350, a previouslyauthorized virtual machine can be denied access. Additionally,authorization system 350 can monitor an activity status of virtualmachines. When a particular virtual machine that previously was grantedcredentials becomes inactive or de-instantiated, then the credentialsfor that virtual machine can be invalidated by authorization system 350.The invalid status can be proactively reported to audit log system 360or can be provided responsive to further audit data storage attemptsusing the credentials. This invalidation of credentials for a particularvirtual machine can provide a more secure operating environment sinceanother virtual machine cannot use the credentials of a first virtualmachine, such as when a second virtual machine is replicated from thefirst virtual machine.

Returning to the elements of FIG. 3, execution systems 330 and 340 caneach be included in separate cloud computing systems, such as providedby different CSPs. The cloud computing environment can include adistributed computing environment with one or more physical serversdistributed over one or more geographic areas. A plurality of virtualmachines can be instantiated from a single shared virtual machine imageresponsive to user demand, load conditions, throughput needs, amongother factors. For example, system load or access requests may increasedue to end user demand. For instance, any of virtual machines 331, 333,341, and 343 may be hosting an e-commerce or healthcare web site. Atcertain times there may be bursts of spikes in end-user requests. Forexample, in an e-commerce web site, there may be increased activity andthere may be spikes or bursts of end-user activity. In order toaccommodate the increased number of requests, a virtual machine may beprogrammed to replicate or spawn to increase bandwidth to theapplication service. In other examples, an administrator or otherpersonnel may send a request to replicate or spawn a virtual machine.Different identities can be provided by each instance or replication ofa virtual machine to allow that virtual machine to retrieve auditcredentials from authorization system 350.

Cloud computing environments that provide execution systems 330 and 340are representative of any physical or virtual computing system, device,or collection thereof capable of hosting all or a portion of servicesprovided to end users. Examples of cloud computing environment include,but are not limited to, server computers, web servers, applicationservers, rack servers, blade servers, virtual machine servers, or towerservers, as well as any other type of computing system, of whichcomputing system 501 illustrated in FIG. 5 is representative.

Although not shown in FIG. 3 for clarity, computing system 300 caninclude network routing elements and network traffic handling elements.These network routing and handling elements can include wired orwireless network elements, such as packet networks and packet links thatcan each use metal, glass, optical, air, space, or some other materialas the transport media. The network routing and handling elements caneach use various communication protocols, such as Internet Protocol(IP), Ethernet, Time Division Multiplex (TDM), asynchronous transfermode (ATM), synchronous optical networking (SONET), hybrid fiber-coax(HFC), Universal Serial Bus (USB), circuit-switched, communicationsignaling, wireless communications, or some other communication format,including combinations, improvements, or variations thereof. Thesenetwork routing and handling elements can include direct links or caninclude intermediate networks, systems, or devices, and can includelogical network links transported over multiple physical links. Thesenetwork routing and handling elements can each include many differentsignals sharing the same associated link comprising resource blocks,access channels, paging channels, notification channels, forward links,reverse links, user communications, communication sessions, overheadcommunications, carrier frequencies, other channels, timeslots,spreading codes, transportation ports, logical transportation links,network sockets, packets, or communication directions.

Virtual machines 331, 333, 341, and 343, along with any otherinstantiated or replicated virtual machines, can provide an applicationservice to end users. This application service can be representative ofany application, software application, module, component, or collectionthereof hosted in computing system 300. Examples of an applicationservice include, but are not limited to, healthcare applications,financial application, banking applications, credit card paymentapplications, electronic payment applications, email applications,gaming applications, real-time communication applications, blogging andmicro-blogging applications, social networking applications, ande-commerce applications, as well as any other type of application.Application services may be locally installed and executed applications,streamed applications, mobile applications, or any combination orvariation thereof. In some implementations, the application services maybe a browser-based application that executes in the context of a browserapplication.

Authorization system 350 comprises computer processing systems andequipment. Authorization system 350 can include communication or networkinterfaces, as well as computer systems, microprocessors, circuitry,cloud-based systems, or some other processing devices or softwaresystems, and can be distributed among multiple processing devices.Examples of authorization system 350 can also include software such asan operating system, logs, databases, utilities, drivers, networkingsoftware, and other software stored on a computer-readable medium.

Audit log system 360 includes computers, physical servers, virtualmachines, virtual servers, applications, shared data resources, andshared databases. Audit log system 360 can be representative of anyphysical or virtual computing systems, devices, or collections thereofcapable of providing digital data resources to a virtual machine.

Audit system 320 comprises computer processing systems and equipment.Audit system 320 can include communication or network interfaces, aswell as computer systems, microprocessors, circuitry, cloud-basedsystems, or some other processing devices or software systems, and canbe distributed among multiple processing devices. Examples of auditsystem 320 can also include software such as an operating system, logs,databases, utilities, drivers, networking software, and other softwarestored on a computer-readable medium.

FIG. 5 illustrates computing system 501 that is representative of anyapparatus, system, or collections thereof suitable for implementing anaccess control service, access control node, a cloud computing resource,user terminal, or all of the above. Computing 501 is suitable forimplementing user interface system 110, storage system 120, executionsystem 130, authorization system 140, or resource 150 of FIG. 1,although these could use alternative configurations. Computing 501 isalso suitable for implementing execution system 330, execution system340, authorization system 350, audit log system 360, or audit system 320of FIG. 3, although these could use alternative configurations.

Examples of computing system 501 include server computers, rack servers,web servers, cloud computing platforms, and data center equipment, aswell as any other type of physical or virtual server machine, and anyvariation or combination thereof. In some implementations, a collectionof multiple computing systems may be employed to implement all orportions of access control service 521, which may be hosted in one ormore data centers, virtual data centers, or any other suitable computingfacilities.

Computing system 501 may be implemented as a single apparatus, system,or device or may be implemented in a distributed manner as multipleapparatuses, systems, or devices. Computing system 501 includes, but isnot limited to, communication interface system 502, processing system503, and user interface 504. In some examples, user interface 504 may beomitted. Processing system 503 is linked to communication interfacesystem 502 and user interface 504. Processing system 503 includesprocessing circuitry 511 and storage system 512 that stores software513.

Processing system 503 loads and executes software 513 from storagesystem 512. When executed by processing system 503 software 513 directsprocessing system 503 to operate as described herein for the variousaccess control services discussed in the foregoing implementations.Computing system 501 may optionally include additional devices,features, or functionality not discussed for purposes of brevity.

Referring still to FIG. 5, processing system 503 may comprise amicroprocessor and other circuitry that retrieves and executes software513 from storage system 512. Processing system 503 may be implementedwithin a single processing device, but may also be distributed acrossmultiple processing devices or sub-systems that cooperate in executingprogram instructions. Examples of processing system 503 include generalpurpose central processing units, application specific processors, andlogic devices, as well as any other type of processing device,combinations, or variations thereof.

Storage system 512 may comprise any non-transitory computer readablestorage media readable by processing system 503 and capable of storingsoftware 513. Storage system 512 may include volatile and nonvolatile,removable and non-removable media implemented in any method ortechnology for storage of information, such as computer readableinstructions, data structures, program modules, or other data. Examplesof storage media include random access memory, read only memory,magnetic disks, optical disks, flash memory, virtual memory andnon-virtual memory, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other suitable storagemedia.

In addition to computer readable storage media, in some implementations,storage system 512 may also include computer readable communicationmedia over which software 513 may be communicated internally orexternally. Storage system 512 may be implemented as a single storagedevice but may also be implemented across multiple storage devices orsub-systems co-located or distributed relative to each other. Storagesystem 512 may comprise additional elements, such as a controller,capable of communicating with processing system 503 or possibly othersystems.

Software 513 may be implemented in program instructions and among otherfunctions may, when executed by processing system 503, direct processingsystem 503 to operate as described herein with respect to the variousoperational scenarios, sequences, and processes. In particular, theprogram instructions may include various components or modules thatcooperate or otherwise interact to carry out the various processes andoperational scenarios described herein. The various components ormodules may be embodied in compiled or interpreted instructions or insome other variation or combination of instructions. The variouscomponents or modules may be executed in a synchronous or asynchronousmanner, serially or in parallel, in a single threaded environment ormulti-threaded, or in accordance with any other suitable executionparadigm, variation, or combination thereof. Software 513 may includeadditional processes, programs, or components, such as operating systemsoftware or other application software. Software 513 may also comprisefirmware or some other form of machine-readable processing instructionsexecutable by processing system 503.

In general, software 513 may, when loaded into processing system 503 andexecuted, transform a suitable apparatus, system, or device (of whichcomputing system 501 is representative) overall from a general-purposecomputing system into a special-purpose computing system customized tofacilitate run-time experimentation with user interface configurationsas described herein for each implementation. Indeed, encoding software513 on storage system 512 may transform the physical structure ofstorage system 512. The specific transformation of the physicalstructure may depend on various factors in different implementations ofthis description. Examples of such factors may include, but are notlimited to, the technology used to implement the storage media ofstorage system 512 and whether the computer-storage media arecharacterized as primary or secondary storage, as well as other factors.

For example, if the computer readable storage media are implemented assemiconductor-based memory, software 513 may transform the physicalstate of the semiconductor memory when the program instructions areencoded therein, such as by transforming the state of transistors,capacitors, or other discrete circuit elements constituting thesemiconductor memory. A similar transformation may occur with respect tomagnetic or optical media. Other transformations of physical media arepossible without departing from the scope of the present description,with the foregoing examples provided only to facilitate the presentdiscussion.

It should be understood that computing system 501 is generally intendedto represent a computing system or systems on which software 513 may bedeployed and executed in order to implement access control services in acloud computing environment. However, computing system 501 may also besuitable as any computing system on which software 513 may be staged andfrom where software 513 may be distributed, transported, downloaded, orotherwise provided to yet another computing system for deployment andexecution, or yet additional distribution.

Communication interface system 502 may include communication connectionsand devices that allow for communication with other computing systems(not shown) over a communication network or collection of networks (notshown). Examples of connections and devices that together allow forinter-system communication may include network interface cards,antennas, power amplifiers, RF circuitry, transceivers, and othercommunication circuitry. The connections and devices may communicateover communication media to exchange communications with other computingsystems or networks of systems, such as metal, glass, air, or any othersuitable communication media. The aforementioned media, connections, anddevices are well known and need not be discussed at length here.

Communication between computing system 501 and any other computingsystem (not shown) may occur over a communication network or networksand in accordance with various communication protocols, combinations ofprotocols, or variations thereof. Examples of communication networksover which computing system 501 may exchange information with othercomputing systems include intranets, the Internet, local area networks,wide area networks, wireless networks, wired networks, virtual networks,software defined networks, data center buses, computing backplanes,networks, or any combination or variation thereof. The aforementionedcommunication networks and protocols are well known and need not bediscussed at length here. However, some communication protocols that maybe used include, but are not limited to, the Internet protocol (IP,IPv4, IPv6, etc.), the transfer control protocol (TCP), and the userdatagram protocol (UDP), as well as any other suitable communicationprotocol, variation, or combination thereof.

In any of the aforementioned examples in which information is exchanged,the exchange of information may occur in accordance with any of avariety of protocols, including FTP (file transfer protocol), HTTP(hypertext transfer protocol), REST (representational state transfer),WebSocket, DOM (Document Object Model), HTML (hypertext markuplanguage), CSS (cascading style sheets), HTML5, XML (extensible markuplanguage), JavaScript, JSON (JavaScript Object Notation), and AJAX(Asynchronous JavaScript and XML), as well as any other suitableprotocol, variation, or combination thereof. In some implementations,information may be exchanged in accordance with any of a variety ofemail protocols, including without limitation POP (Post OfficeProtocol), IMAP (Internet Message Access Protocol), MAPI (MessagingApplication Programming Interface), HTTP mail, or any other suitableemail protocol.

User interface system 504 may include a keyboard, a mouse, a voice inputdevice, a touch input device for receiving a touch gesture from a user,a motion input device for detecting non-touch gestures and other motionsby a user, and other comparable input devices and associated processingelements capable of receiving user input from a user. Output devicessuch as a display, speakers, haptic devices, and other types of outputdevices may also be included in user interface system 504. In somecases, the input and output devices may be combined in a single device,such as a display capable of displaying images and receiving touchgestures. The aforementioned user input and output devices are wellknown in the art and need not be discussed at length here.

User interface system 504 may also include associated user interfacesoftware executable by processing system 503 in support of the varioususer input and output devices discussed above. Separately or inconjunction with each other and other hardware and software elements,the user interface software and user interface devices may support agraphical user interface, a natural user interface, or any other type ofuser interface. In addition, user input made with respect to the userinterfaces can be input via user interface system 504.

The functional block diagrams, operational scenarios and sequences, andflow diagrams provided in the Figures are representative of exemplarysystems, environments, and methodologies for performing novel aspects ofthe disclosure. While, for purposes of simplicity of explanation,methods included herein may be in the form of a functional diagram,operational scenario or sequence, or flow diagram, and may be describedas a series of acts. It is to be understood and appreciated that themethods are not limited by the order of acts, as some acts may, inaccordance therewith, occur in a different order and/or concurrentlywith other acts from that shown and described herein. For example, thoseskilled in the art will understand and appreciate that a method couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, not all acts illustratedin a methodology may be required for a novel implementation.

The descriptions and figures included herein depict specificimplementations to teach those skilled in the art how to make and usethe best option. For the purpose of teaching inventive principles, someconventional aspects have been simplified or omitted. Those skilled inthe art will appreciate variations from these implementations that fallwithin the scope of the invention. Those skilled in the art will alsoappreciate that the features described above can be combined in variousways to form multiple implementations. As a result, the invention is notlimited to the specific implementations described above, but only by theclaims and their equivalents.

What is claimed is:
 1. A method of controlling access to audit loggingresources by an instantiated virtual machine from among a plurality ofinstantiated virtual machines in a virtual computing environment, themethod comprising: the instantiated virtual machine receiving a usertoken; the instantiated virtual machine sending a request forindividualized audit credentials from an authorization system, whereinthe request is based on the user token and an identity, wherein theidentity identifies the instantiated virtual machine; and theinstantiated virtual machine receiving the individualized auditcredentials from the authorization system based at least on the usertoken and the identity, the individualized audit credentials enablingauthorized storage of first audit data in an audit system, wherein thefirst audit data pertains to the instantiated virtual machine, and theauthorized storage is authorized by the audit system; the instantiatedvirtual machine actively operating, with the individualized auditcredentials, through a first time period; wherein when the instantiatedvirtual machine experiences, after the first time period, an eventselected from failing verification based on the identity or having theindividualized audit credentials revoked, the event is effective tocause de-authorization of the instantiated virtual machine and reportingof information regarding the de-authorized instantiated virtual machineto the audit system, and wherein the de-authorization of theinstantiated virtual machine comprises determining when the instantiatedvirtual machine has been de-instantiated, and responsively allowing forde-authorization of the individualized audit credentials of thede-authorized de-instantiated instantiated virtual machine.
 2. Themethod of claim 1, wherein the identity comprises a unique numbergenerated by the instantiated virtual machine.
 3. The method of claim 1,wherein the identity comprises a network address of the instantiatedvirtual machine.
 4. The method of claim 1, wherein the user token isreceived by the instantiated virtual machine during instantiation of theinstantiated virtual machine.
 5. The method of claim 1, wherein theauthorized storage is enabled responsive to the audit system verifyingthe individualized audit credentials with the authorization system andresponsively receiving an authorization status transferred by theauthorization system.
 6. The method of claim 1, wherein the informationregarding the de-authorized instantiated virtual machine comprises theindividualized audit credentials of the de-authorized instantiatedvirtual machine.
 7. The method of claim 1, wherein the storage of thefirst audit data is based at least on the individualized auditcredentials accompanying the first audit data.
 8. The method of claim 7,wherein the instantiated virtual machine is authorized to store thefirst audit data based on the authorization system receivingauthorization check messages transferred by the audit system andresponsively providing the audit system with authorization statusmessages indicating that the instantiated virtual machine is authorizedto store the first audit data.
 9. A computing system configured tocontrol access to audit logging resources by virtual machines, thecomputing system comprising software instructions stored on at least onenon-transitory computer-readable storage medium, wherein the softwareinstructions are configured, when executed by one or more processors, toenable the computing system to: receive a request from an instantiatedvirtual machine from among a plurality of instantiated virtual machinesfor audit credentials, wherein the request is based on at least a usertoken and an identity from the instantiated virtual machine; provide, inresponse to the request, individualized audit credentials to theinstantiated virtual machine based at least on the user token and theidentity; authorize storage of audit data transferred by theinstantiated virtual machine over a first period of time based at leaston the individualized audit credentials; and de-authorize theinstantiated virtual machine, after the first period of time, and reportinformation regarding de-authorization of the instantiated virtualmachine, responsive to at least one of the following: failedverification of the instantiated virtual machine based on the identity,or revocation of the individualized audit credentials; and wherein thede-authorization of the instantiated virtual machine comprisesdetermining when the instantiated virtual machine has beende-instantiated, and responsively allowing for de-authorization of theindividualized audit credentials of the de-authorized de-instantiatedinstantiated virtual machine.
 10. The computing system of claim 9,wherein the identity comprises a unique number generated by theinstantiated virtual machine.
 11. The computing system of claim 9,wherein the identity comprises a network address of the instantiatedvirtual machine.
 12. The computing system of claim 9, wherein theidentity comprises an access token provided to the instantiated virtualmachine during instantiation of the instantiated virtual machine. 13.The computing system of claim 9, wherein the software instructions areconfigured, when executed by one or more processors, to enable thecomputing system to: authorize storage of the audit data transferred bythe instantiated virtual machine by at least checking the individualizedaudit credentials with an authorization system and responsivelyreceiving an authorization status transferred by the authorizationsystem.
 14. The computing system of claim 9, wherein the softwareinstructions are configured, when executed by one or more processors, toenable the computing system to: de-authorize the instantiated virtualmachine by at least determining when the instantiated virtual machinehas been de-instantiated, and responsively de-authorizing theindividualized audit credentials of the de-authorized instantiatedvirtual machine.
 15. The computing system of claim 9, wherein theinformation regarding the de-authorized instantiated virtual machinecomprises the individualized audit credentials of the de-authorizedinstantiated virtual machine.
 16. The computing system of claim 9,wherein the software instructions are configured, when executed by oneor more processors, to enable the computing system to: store the auditdata transferred by the instantiated virtual machine based at least onthe individualized audit credentials accompanying the audit data. 17.The computing system of claim 16, wherein the software instructions areconfigured, when executed by one or more processors, to enable thecomputing system to: receive authorization check messages transferred byan audit system and responsively provide authorization status messagesfor delivery to the audit system indicating whether the instantiatedvirtual machine is authorized to store the audit data.
 18. Acomputer-implemented method for controlling access to audit loggingresources by a plurality of virtual machines, the method comprising:receiving a request from an instantiated virtual machine for auditcredentials, wherein the request is based on at least a user token andan identity received from the instantiated virtual machine; providing,in response to the request, individualized audit credentials to theinstantiated virtual machine based at least on the user token and theidentity; authorizing storage of audit data, in an audit system,transferred by the instantiated virtual machine based at least on theindividualized audit credentials; and de-authorizing the instantiatedvirtual machine and reporting information regarding de-authorization ofthe instantiated virtual machine, responsive to at least one of thefollowing: failed verification of the instantiated virtual machine basedon the identity, or revocation of the individualized audit credentials;and wherein the de-authorization of the instantiated virtual machinecomprises determining when the instantiated virtual machine has beende-instantiated, and responsively allowing for de-authorization of theindividualized audit credentials of the de-authorized de-instantiatedinstantiated virtual machine.
 19. The computer-implemented method ofclaim 18, wherein the user token is provided to the instantiated virtualmachine during instantiation of the instantiated virtual machine. 20.The computer-implemented method of claim 18, wherein the authorizedstorage is enabled responsive to the audit system verifying theindividualized audit credentials with an authorization system andresponsively receiving an authorization status transferred by theauthorization system.
 21. The computer-implemented method of claim 18,wherein the information regarding de-authorization of the instantiatedvirtual machine comprises the individualized audit credentials of thede-authorized instantiated virtual machine.
 22. The computer-implementedmethod of claim 18, wherein the instantiated virtual machine isauthorized to store the first audit data based on an authorizationsystem receiving authorization check messages transferred by the auditsystem and responsively providing the audit system with authorizationstatus messages indicating that the instantiated virtual machine isauthorized to store the first audit data.